@andig I took your branch fix/ocpp-initial-status-3 made to resolve #15677 and performed some debugging to resolve #18443. It was successfully initializing with the eProwallbox that does not support remote trigger after my changes.

Basically, the changes are:

1. Fix a panic in 8adb8fe. The original code was accessing cs.regs[chargePoint.ID()].cp which was not existing yet.
2. Change the order of caching status and calling cp.OnStatusNotification(request) in 67fe269. Without this change, the caching never happened since in the moment the function is called, cs.ChargepointByID(id) already succeeds, only the connector is not available yet. With the change it will now always do the caching, but I think this is no issue since the cached status is only used during init. Commit 5c3fb4a fixed a mutex deadlock I introduces with the change.
3. Use the cached status when the charger does not support RemoteTrigger in 236ed2a. In addition, I guarded all other calls to TriggerMessageRequest with HasRemoteTriggerFeature